Add Python 3.13#207
Conversation
|
This is now failing as Sounds like we should prioritize dropping |
|
I wrote up an automation script that we can use to convert all RAPIDS repositories from Even if we dropped In the interest of keeping our total work at a minimum: if cupy and other RAPIDS dependencies become available for Python 3.13 but still haven't finished the |
Upstream has archived `boa` and recommended moving to `rattler-build`. So this drops `boa` from our images. Also as `boa` does not support Python 3.13 (unmaintained), dropping `boa` is a prerequisite to adding Python 3.13. There are other dependencies it pins to old versions that will be able to get updates too. We tried dropping this before, but it caused issues with the RAPIDS 25.02 release. Once the RAPIDS 25.02 release is complete, let's give this another try.
|
This should be unblocked now. |
jameslamb
left a comment
jameslamb
left a comment
There was a problem hiding this comment.
Double-checked a couple build logs, saw the things I expected... the right build-string filters to say "only give us CPython", the right Python versions installed, and no new warnings to worry about.
I'm ok with duplicating the PYTHON_*_VERSION logic in the Dockerfile instead of doing that in compute-build-args.sh, think that's fine.
3 participants
This PR adds Python 3.13 CI images for
ci-wheelandcitestwheel.For now we are blocked by conda-forge/conda-feedstock#246 on adding Python 3.13 support to our conda CI images. However, I went ahead and did some refactoring that will be needed for conda support once that is available.